<html>
<head>
<link rel="shortcut icon" href="./favicon.ico">
<link rel="stylesheet" type="text/css" href="./style.css">
<link rel="canonical" href="./tools.html">
<meta name="viewport" content="width=device-width, initial-scale=1">
<meta name="description" content="Various little tools I use for digital design and Verilog coding.">
<title>Tools Used To Write This Book</title>
</head>
<body>

<h1>Tools Used To Write This Book</h1>

<ul>

<li><a href="./v2h.py">v2h.py</a>, which converts commented Verilog files into
HTML files. Comments are processed as Markdown. Thus, the web page doesn't get
stale as the code evolves.

<li><a href="./verilinter">verilinter</a>, which is a small script using <a
href="https://www.veripool.org/wiki/verilator">Verilator</a> and <a
href="https://iverilog.icarus.com/">Icarus Verilog</a> to lint Verilog-2001
files. This little tool catches a lot of simple and not so simple Verilog
mistakes and corner cases.

<li><a href="https://www.intel.com/content/www/us/en/software/programmable/quartus-prime/download.html">Intel Quartus Prime</a>.
The CAD tool suite for Intel (ex-Altera) FPGAs. It's smaller and easier to run
than Xilinx Vivado, and produces excellent post-elaboration and post-synthesis
diagrams, which are very useful for debugging designs.

<li>The particular look-and-feel of this site comes from the
<a href="./style.css">style.css</a> file.
It's pretty basic, but makes sure all pages
look the same on pretty much any browser.

</ul>

<hr><a href="./index.html">Back to FPGA Design Elements</a>
</body>
</html>
